Release Upgrade Kicksecure 16 to Kicksecure 17
How to Release Upgrade from Kicksecure 16 to Kicksecure 17
Notices[edit]
Table: Release Upgrade Kicksecure Notices
Notice | Description |
---|---|
Difficulty |
|
Release Upgrade vs Re-Installation |
To use Kicksecure 17, users can either:
|
Standard Updates |
|
Automated Release Upgrade vs Manual Release Upgrade |
|
Configuration Files Resets | Since this is an automated release upgrade, user modified configuration files (if any) in folder /etc will be reset, overwritten with the Debian or Kicksecure package version. The user is free to restore the configuration after the release upgrade.
|
High Level Overview[edit]
- Backup all data - ideally have a copy of the VM(s) so it is possible to try again (if necessary).
- Perform the usual standard ("everyday") update instructions.
- Consider running the optional sanity tests.
- Release Upgrade Kicksecure
- Power off Kicksecure
- Release Upgrade Kicksecure
- Restart Kicksecure
- Restart Kicksecure
Sanity Tests[edit]
These are optional, but recommended. To complete sanity tests, please press on expand on the right.
sudo dpkg --audit ; echo $?
Expected output.
sudo dpkg --configure -a ; echo $?
Expected output.
sudo apt update
sudo apt full-upgrade
For testing purposes, install package nano
.
sudo apt install nano ; echo $?
## ... successful installation of nano ... 0
Apt install fix missing.
sudo apt install -f
Expected upgrade.
Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Release Upgrade[edit]
- Backup all data - ideally have a clone of the VM(s) so it is possible to try again (if necessary).
- Perform the usual standard ("everyday") update instructions.
- Consider running the optional sanity tests.
- Run systemcheck.
- View
release-upgrade
command version. cat /usr/sbin/release-upgrade | grep version= - Check
release-upgrade
command version. Should be minimum2.0
, should showversion="2.0"
. - Consider keeping the full release upgrade log output. It will be required for Support in case there are issues.
- Perform the automated release upgrade using
release-upgrade
command. sudo release-upgrade - Done. If everything went well, at the end it will show:
INFO: OK. (release-upgrade version: 2.0) Release upgrade success.
- Reboot.
- Optional, recommended: Re-install Meta Packages and Safely Run Autoremove
Footnotes[edit]
- ↑
This method is still possible. All the automated
release-upgrade
script does is perform actions which the user could perform manually. If a manual release upgrade is desired, emulate what therelease-upgrade
script is doing. The manual release upgrading procedure is undocumented due to the size of the instructions and duplication involved.
We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!